You'll need to modify /src/cake.coffee as well...

Oh, I'm an idiot. Yes.

All right, updated both the .coffee and the .js now.

I'm not sure this works as a solution, actually -- as long as there are existing invoke() calls that don't supply a callback, then it's still kind of a mess.

So, here's the deal with Cake -- it's just a tiny little shim for exposing your top-level CoffeeScript functions to the command-line:

http://jashkenas.github.com/coffee-script/documentation/docs/cake.html

... not a full-featured Rake-style library with dependency resolution, nested tasks, etc etc. The idea is that those things: composing multiple async events, determining the order in which a series of functions should be run, defining a complex API -- are all things better done in regular code, and not a wimpy DSL. Once you have your code sorted out, instead of stuffing all of the important reusable logic into Cake tasks, just expose the bits you want accessible to the command-line via Cake. Does that sound reasonable?

Yeah, I think that's pretty much how it has to work. Callbacks are pretty much an all-or-nothing thing in node. Node fail rather than cake fail I guess.

Jeremy (or anyone who knows...), could you post an example of how to invoke a module that does async stuff from a Cakefile? I've tried code both in the Cakefile and in a separate .coffee module required by the Cakefile and either way my main process exits before my async code is done executing. I'm trying to use child_process.spawn to launch mocha tests.